Autonomous Agents Agentic Workflow
PM: Drive Ticket — Autonomous Agents Automation Workflow
Drive a ticket to completion — plan, dispatch SE/QA, track PRs, merge, validate, close. Idempotent.
sidebutton install Autonomous Agents Inputs
- type
- string
- description
- Jira ticket URL (parent with subtasks, or ticket to plan)
- type
- string
- default
- description
- Optional extra instructions for the agent
- type
- string
- default
- ~/workspace
- description
- Working directory for the agent
Allowed Domains
Unrestricted — no domain lock enforced.
Step Summary
2 steps using step types: terminal.openterminal.run
.
Workflow Definition
YAML source for the ops/agent_pm_drive.yaml workflow. This is the complete definition executed by the SideButton MCP server when Autonomous Agents agents run this automation.
schema_version: 1
id: agent_pm_drive
title: "PM: Drive Ticket"
description: "Drive a ticket to completion — plan, dispatch SE/QA, track PRs, merge, validate, close. Idempotent."
category:
level: pipeline
domain: engineering
metadata:
agent: true
role: pm
params:
ticket_url:
type: string
description: "Jira ticket URL (parent with subtasks, or ticket to plan)"
hint:
type: string
default: ""
description: "Optional extra instructions for the agent"
entry_path:
type: string
default: "~/workspace"
description: "Working directory for the agent"
steps:
- type: terminal.open
title: "Agent: PM Drive Ticket"
cwd: "{{entry_path}}"
- type: terminal.run
cmd: >-
source ~/.agent-env && claude --dangerously-skip-permissions
"you are a PM agent. your mission: drive {{ticket_url}} to completion. this workflow is IDEMPOTENT — re-dispatch until the ticket is Done.
read the ticket, all subtasks, and recent comments. BEFORE planning or dispatching: learn how to PM relevant parts — load skill packs for the domain and each affected module. use this product knowledge for gap analysis and dispatch decisions.
detect phase:
PLAN (no subtasks exist):
gap analysis using product knowledge from skill packs — for each requirement, what exists vs what needs to change.
decompose into subtasks — each is one shippable behavior change with observable acceptance criteria, sized for one SE session.
assign execution groups by dependency. create subtasks in Jira. post plan summary comment.
REFINE (subtasks exist but plan has gaps):
check each subtask: clear scope? specific acceptance criteria? correct dependencies? right execution group?
check overall: all parent requirements covered? dependency chain valid?
create missing subtasks, update incomplete ones. post refinement comment.
MANAGE (subtasks ready for work):
for each subtask, take the next lifecycle action:
To Do → dispatch agent_se_work.
In Review + CI passing → dispatch agent_qa_validate (PR# in hint). CI failing → dispatch agent_se_followup.
QA PASS → merge PR → Done. QA FAIL → dispatch agent_se_followup.
bugs found by QA → create Bug tickets, dispatch agent_se_work.
silent failure (idle agent + no comment) → re-dispatch to a DIFFERENT agent.
after merging → dispatch agent_pull_repos to idle agents. respect execution group order.
try to avoid dispatching jobs to yourself — you are the PM orchestrator, not a worker. check fleet status and prefer dispatching to other idle agents.
VALIDATE & CLOSE (all subtasks Done, PRs merged):
verify on live site. bugs found → new subtasks, stay in MANAGE. clean → transition parent to Done.
post one status comment: progress (N/M done), actions taken, blockers, next steps.
{{hint}}"
How To Run
Install the Autonomous Agents knowledge pack into your SideButton agent, then dispatch this workflow by its ID ops/agent_pm_drive.yaml. Agents invoke it directly via the MCP protocol or through the portal.